fix(memory): empty memory case - #6322

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Aug 6, 2026 9:04am

PR Summary

Low Risk
Scoped bug fix on an existing empty-read code path with contract alignment and tests; no change to auth or write paths beyond response shaping for misses.

Overview
Fixes Memory Get lookups when no conversation exists yet: internal tool execution was failing because the empty-result path returned a plain JSON body without the verified private-tool metadata that successful reads already attach via createMemoryResponse.

The no-match branch now routes through createMemoryResponse with memories: [], so callers that send the provenance request header get a complete, empty provenance bundle and the matching response header; ordinary callers still receive { success: true, data: null } with no extra fields or headers.

The get-by-id API contract now types data as nullable to match real responses. Vitest coverage asserts both the tool-metadata and headerless empty behaviors.

^{Reviewed by Cursor Bugbot for commit 47e9298. Configure here.}

Greptile Summary

This PR fixes empty Memory lookups by routing them through the existing provenance-aware response helper and updates the API contract to permit the established null result.

• Emits verified exact-empty provenance metadata for internal tool requests when no matching memory exists.
• Preserves the existing headerless response for ordinary API callers.
• Adds route tests for both provenance-aware and ordinary empty responses.

Confidence Score: 5/5

The PR appears safe to merge with no actionable correctness or security issues identified.

The empty-result path now produces the metadata envelope required by internal tools, ordinary callers retain their prior response, and the contract accurately accepts the route’s null result.

_{Reviews (1): Last reviewed commit: "fix(memory): provenance checks" | Re-trigger Greptile}